Description

Roles

Attributes

Steps

1. Review the requirements to be tested:

   Work with Analyst and Developer to identify which scenarios need new or additional test cases. Review the Iteration Plan to ensure you understand the scope of development for the current iteration.

2. Identify relevant Test Cases:

   Identify paths through the scenario as unique test conditions. Consider alternative or exception paths from both a positive and negative perspective.

    

   Discuss the requirement with the Stakeholder to identify other conditions of satisfaction for the requirement.

    

   List the test cases with a unique name that identifies the condition they evaluate or their expected result.

3. Outline the Test Cases:

   For each test case, write a brief description with an expected result. Ensure that a casual reader can clearly understand the difference between test cases. Note the logical pre-conditions and post-conditions that apply to each test case. Optionally, outline steps for the test case.

    

   Verify that test cases meet the Test Case guidelines. For more information on the test case, see Test Case Template.

4. Identify test data needs:

   Review each test case and note where data input or output might be required. Identify the type, quantity, and uniqueness of the required data, and add these observations to the test case. Focus on articulating the data needed and not on creating specific data.

    

   For more information on test data selection, see Test Case checklist.

5. Share and evaluate the Test Cases:

   Walk through the test cases with the Analyst and Developer responsible for the related scenario. Ideally, the Stakeholder also participates.

    

   Ask the participants to agree that if these test cases pass, they will consider these requirements implemented. Elicit additional test ideas from the Analyst and the Stakeholder to ensure you understand the expected behavior of the scenario.

    

   During the walkthrough, ensure that:

   • The Use Cases and Supporting Requirements Specification planned for the current iteration have test cases.
   • All the participants agree with the expected results of the test cases.
   • There are no other conditions of satisfaction for the requirement being tested, which indicates either a missing test case or a missing requirement.

Inputs and Outputs

WorkProduct	Input	Output	Allowable States
Supporting Requirements Specification			(none)
Test Case			(none)
Use Case			(none)

Other Instances

Instance Parent
OpenUP (with RACI and Entry_Exit criteria)Inception Iteration [1..n]Identify and Refine Requirements (Inception Iteration [1..n])
OpenUP (with RACI and Entry_Exit criteria)Construction Iteration [1..n]Identify and Refine Requirements (Construction Iteration [1..n])